refactor: move NullComm from NDSL to pace#168
Conversation
We decided to remove `NullComm` from NDSL in favor of `MPIComm` and `LocalComm`, see NOAA-GFDL/NDSL#318 for context. pace exposes a `NullCommConfig` and is heavily relying on `NullComm` in tests. We thus suggest to move `NullComm` to `pace/comm.py`.
|
@oelbert I'd like to move on this PR. It is blocking NOAA-GFDL/NDSL#350, which we scheduled for the next NDSL release. Is there anything I can do from my side to get traction on this PR? To follow up on our quick discussion about |
|
If you could write a quick issue that'd be great, and I'll queue the merge |
|
Though we'll have to actually change it to LocalComm for some of the tests in PyFV3 and PySHiELD but that's lower priority |
Follow-up issue #172. Thanks for hitting all the buttons today 🙏 |
Description
We decided to remove
NullCommfrom NDSL in favor ofMPICommandLocalComm, see NOAA-GFDL/NDSL#318 for context. pace exposes aNullCommConfigand is heavily relying onNullCommin tests. We thus suggest to moveNullCommtopace/comm.py./cc @FlorianDeconinck
How Has This Been Tested?
Did a search and manual replace of
NullCommimports. CI is still green. Copied over a simple test from NDSL.Checklist: